Methods and systems for collecting pharmaceutical containers

ABSTRACT

A pharmaceutical order filling system receives pharmaceutical orders and uses an accumulation device to accumulate bottles of pharmaceuticals corresponding to the pharmaceutical orders. The accumulation device is configured with a table assembly that includes a plurality of holding tubes configured to accumulate multiple bottles corresponding to pharmaceutical orders. The accumulation device also includes a bottle pick and place assembly configured to place bottles into holding tubes and an unload assembly configured to empty accumulated bottles from holding tubes into an unload assembly tube. The accumulation device may be further configured to receive and temporarily store a single bottle of a prescription order. The accumulation device may be configured to release accumulated bottles onto a conveyor in an upright position.

FIELD

The present disclosure relates generally to the technical field ofautomated filling centers. In a specific example, the present disclosuremay relate to a high volume fulfillment center, (e.g., a high volumepharmacy) and to systems and devices used in filling prescriptions andprescription orders at a high volume pharmacy.

BACKGROUND

A high-volume pharmacy may process and fill a large number ofprescriptions and prescription orders. Automated systems may be used bya high volume pharmacy to process and fulfill prescriptions.

Frequently, more than one prescription drug is required to complete aprescription order. Portions of the prescription order may be fulfilledin different areas of the high-volume pharmacy. After fulfillment, thefulfilled prescriptions may be gathered into a complete prescriptionorder for shipping.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example system, according to an exampleembodiment;

FIG. 2 is a block diagram of an example order processing device that maybe deployed within the system of FIG. 1, according to an exampleembodiment;

FIG. 3 is a perspective of a bottle that may be used in the system ofFIG. 1, according to an example embodiment;

FIG. 4 is a block diagram of an accumulation device that may be deployedwithin the system of FIG. 1, according to an example embodiment;

FIG. 5 is an end view of the accumulation subsystem of the accumulationdevice of FIG. 4, according to an example embodiment;

FIG. 6 is a top view of the accumulation subsystem of FIG. 5, accordingto an example embodiment;

FIG. 7 is a side view of the accumulation subsystem of FIG. 5, accordingto an example embodiment;

FIG. 8 is a perspective view of the accumulation subsystem of FIG. 5,according to an example embodiment;

FIG. 9 is a detailed top view of a rotary assembly that may be deployedwithin the accumulation subsystem of FIG. 5, according to an exampleembodiment;

FIG. 10 is a side view of the rotary assembly of FIG. 9, according to anexample embodiment;

FIG. 11 is a perspective view of an upper gantry that may be deployedwithin the accumulation subsystem of FIG. 5, according to an exampleembodiment;

FIG. 12 is an enlarged perspective view of a lower gantry that may bedeployed within the accumulation subsystem of FIG. 5, according to anexample embodiment;

FIG. 13 is a perspective view of a table assembly that may be deployedwithin the accumulation subsystem of FIG. 5, according to an exampleembodiment;

FIG. 14 is a side view of the table assembly of FIG. 13, according to anexample embodiment;

FIG. 15 is a perspective view of a portion of the table assembly of FIG.13, according to an example embodiment;

FIG. 16 is a perspective view of a catch assembly positioned within thetable assembly of FIG. 13, according to an example embodiment;

FIG. 17 is a cross-sectional view of a portion of the table assembly ofFIG. 13 taken along line 17-17;

FIG. 18 is a side view of a portion of a bottle scan and pick assemblyand the z-axis assembly of the upper gantry of FIG. 11;

FIG. 19 is a perspective view of the portion of a bottle scan and pickassembly and the z-axis assembly of the upper gantry of FIG. 18;

FIG. 20 is a perspective view of an unload assembly and the z-axisassembly of the lower gantry of FIG. 12;

FIG. 21 is a side, cross-sectional view of the unload assembly and thez-axis assembly of the lower gantry of FIG. 20 along line 21-21 of FIG.20;

FIG. 22 is a side view of a bottle escapement assembly within theaccumulation subsystem of FIG. 5, according to an example embodiment;

FIG. 23 is a cross-sectional view of the bottle escapement assemblyalong line 23-23 of FIG. 22;

FIG. 24 is a diagram of a control subsystem within the accumulationdevice of FIG. 4, according to an example embodiment;

FIG. 25 is an example process flow illustrating a method of accumulatingpharmaceutical bottles of a prescription order, according to an exampleembodiment; and

FIG. 26 is a block diagram of a machine in the example form of acomputer system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed or stored.

DETAILED DESCRIPTION

Example systems and methods for collecting pharmaceutical containers,such as for shipment or other delivery, are described. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding of exampleembodiments. It will be evident, however, to one of ordinary skill inthe art that embodiments may be practiced without these specificdetails.

Generally, a prescription order is generated for a high volume pharmacy.The prescription order may include one or more than one prescriptiondrug for fulfillment. Each prescription drug in a prescription order isan order component of the prescription order. Generally, the ordercomponents are pill containers or containers and packaging having aquantity of a prescription drug contained therein.

Multiple order components of a prescription order may be prepared atdifferent times. The steps required for preparation, quality control, orotherwise reviewing or processing a particular order component of aprescription order may differ from the steps required for another ordercomponent of a prescription order. It may be useful to hold, accumulateor otherwise consolidate one or more order components of a prescriptionorder while one or more other order components of the prescription orderare prepared, undergo quality control, or otherwise reviewed orprocessed at a high volume pharmacy. An accumulation device may bedeployed to facilitate accumulation or consolidation of one or moreorder components of a prescription order.

FIG. 1 is a block diagram of an example implementation of a system 100,according to an example embodiment. While the system 100 is generallydescribed as being deployed in a high volume pharmacy or fulfillmentcenter (e.g., a mail order pharmacy, a direct delivery pharmacy, anautomated pharmacy, multiple package delivery center, and the like), thesystem 100 and/or components thereof may otherwise be deployed (e.g., ina lower volume pharmacy). A high volume pharmacy may be a pharmacy thatis capable of filling prescriptions automatically, mechanically,manually, or a combination thereof. The system 100 may include a benefitmanager device 102, a pharmacy device 106, and a user device 108, whichmay communicate with each other directly and/or over a network 104. Thesystem 100 may also include a storage device 110.

The benefit manager device 102 is a device operated by an entity that isat least partially responsible for creation and/or management of thepharmacy or drug benefit. While such an entity operating the benefitmanager device 102 is typically a pharmacy benefit manager (PBM), otherentities may operate the benefit manager device 102 either on behalf ofthemselves, the PBM, another entity, or other entities. For example, thebenefit manager device 102 may be operated by a health plan, a retailpharmacy chain, a drug wholesaler, a data analytics or other type ofsoftware-related company, or the like. In some embodiments, a PBM thatprovides the pharmacy benefit may also provide one or more than oneadditional benefits including a medical or health benefit, a dentalbenefit, a vision benefit, a wellness benefit, a radiology benefit, apet care benefit, an insurance benefit, a long term care benefit, anursing home benefit, and the like. The PBM may, in addition to its PBMoperations, operate one or more than one pharmacy. The pharmacies may beretail pharmacies, mail order pharmacies, specialty pharmacies,pharmaceutical vending machines or kiosks, and the like.

Some of the operations of the PBM that operates the benefit managerdevice 102 may include the following activities and processes. A member(or a person on behalf of the member) of a pharmacy benefit planadministered by or through the PBM attempts to obtain a prescriptiondrug at a retail pharmacy location (e.g., a location of a physicalstore) from a pharmacist or a pharmacist technician. The member may alsoattempt to obtain the prescription drug through mail order drug deliveryfrom a mail order pharmacy location, which may be the high volumepharmacy system 100. In some embodiments, the member may also attempt toobtain the prescription drug directly or indirectly through the use of amachine, such as a kiosk, vending unit, mobile electronic device, or adifferent type of mechanical, electrical, electronic communicationdevice, and/or computing device. Such a machine may be filled with theprescription drug in prescription packaging, which may include multipleprescription components, by the high volume pharmacy system 100.

The member may have a copayment for the prescription drug that reflectsan amount of money that the member is responsible to pay the pharmacyfor the prescription drug. The money paid by the member to the pharmacymay come from personal funds of the member, a health savings account(HSA) of the member or the member's family, a health reimbursementarrangement (HRA) of the member or the member's family, a flexiblespending account (FSA) of the member or the member's family, or thelike. In some instances, an employer of the member may directly orindirectly fund or reimburse the member for the copayments.

The amount of the co-pay required from the member may vary withdifferent pharmacy benefit plans having different plan sponsors orclients and/or prescription drugs. The member's copayment may be based aflat copayment (e.g., $10 or other dollar amounts), co-insurance (e.g.,10% or other percents), and/or a deductible (e.g., for first $500 ofannual prescription drug expenses or other dollar amounts) for certainprescription drugs, certain types and/or classes of prescription drugs,and/or all prescription drugs. The copayment may be stored in thestorage 110 or determined by the benefit manager device 102.

In some instances, the member may not pay the copayment or may only paya portion of the copayment for the prescription drug. For example, ifthe usual and customary cost for a generic version of a prescriptiondrug is $4, and the member's flat copayment is $20 for the prescriptiondrug, the member may only be required to pay $4 to receive theprescription drug. In another example involving a worker's compensationclaim, no copayment may be due by the member for the prescription drug.

In addition, copayments may also vary based on different deliverychannels used for the prescription drug to be received by the member.For example, the copayment for receiving the prescription drug from amail order pharmacy location may be less than the copayment forreceiving the prescription drug from a retail pharmacy location.

In conjunction with receiving the copayment (if any) from the member anddispensing the prescription drug to the member, the pharmacy submits aclaim to the PBM for the prescription drug. After receiving the PBM(e.g., through the benefit manager device 102) may perform certainadjudication operations including verifying eligibility for the member,identifying and/or reviewing an applicable formulary for the member todetermine any appropriate copayment, coinsurance, and deductible for theprescription drug, and performing a drug utilization review (DUR) on themember. The PBM provides a response to the pharmacy (e.g. from thebenefit manager device 102 to the pharmacy device 106) followingperformance of at least some of the aforementioned operations.

As part of the adjudication, a plan sponsor (or the PBM on behalf of theplan sponsor) ultimately reimburses the pharmacy for filling theprescription drug when the prescription drug was successfullyadjudicated.

The aforementioned adjudication operations generally occur before thecopayment is received and the prescription drug is dispensed. However,in some instances these operations may occur simultaneously,substantially simultaneously, or in a different order. In addition, moreor less adjudication operations may be performed as at least part of theadjudication process.

The amount of reimbursement paid to the pharmacy by a plan sponsorand/or money paid by the member may be determined at least partiallybased on the type(s) of pharmacy network in which the pharmacy isincluded. Other factors may also be used to determine the amount inaddition to the type of pharmacy network. For example, if the memberpays the pharmacy for the prescription drug without using theprescription drug benefit provided by the PBM (e.g., by paying cashwithout use of the prescription drug benefit or by use of a so-calledpharmacy discount card offering other negotiated rates), the amount ofmoney paid by the member may be different than when the member uses theprescription or drug benefit. In some embodiments, the amount of moneyreceived by the pharmacy for dispensing the prescription drug and forthe prescription drug itself may be higher than when the member uses theprescription or drug benefit. Some or all of the foregoing operationsmay be performed by executing instructions stored on the benefit managerdevice 102 and/or an additional device.

Examples of the network 104 include Mobile Communications (GSM) network,a code division multiple access (CDMA) network, 3rd GenerationPartnership Project (3GPP), an Internet Protocol (IP) network, aWireless Application Protocol (WAP) network, a WiFi network, or an IEEE802.11 standards network, as well as various combinations thereof. Thenetwork 104 may include an optical network. The network 104 may be alocal area network or a global communication network, such as theInternet. In some embodiments, the network 104 may include a networkdedicated to prescription orders, e.g., a prescribing network such asthe electronic prescribing network operated by Surescripts of Arlington,Va.

Moreover, although the system shows a single network 104, multiplenetworks can be used. The multiple networks may communicate in serieswith each other to link the devices 102, 106-110 or in parallel to linkthe devices 102, 106-110.

The pharmacy device 106 may include an order processing device 114, apharmacy management device 116, and a pharmacy fulfillment device 112 incommunication with each other directly and/or over the network 104.

The order processing device 114 may receive information regardingfilling prescriptions and may direct an order component to one or morethan one of the devices of the pharmacy fulfillment device 112 at apharmacy. The pharmacy fulfillment device 112 may fulfill, dispense,aggregate, and/or pack the order components of the prescription drugs inaccordance with one or more than one of the prescription orders directedby the order processing device 114. The order processing device 114 maybe deployed in the system 100, or may otherwise be used.

In general, the order processing device 114 is a device located withinor otherwise associated with the pharmacy to enable fulfillment of aprescription and dispensing prescription drugs by the pharmacyfulfilment device 112. In some embodiments, the order processing device114 may be an external device separate from the pharmacy and communicatewith other devices located within the pharmacy.

For example, the external order processing device 114 may communicatewith an internal order processing device 114 and/or other deviceslocated within the system 100. In some embodiments, the external orderprocessing device 114 may have limited functionality (e.g., as operatedby a patient requesting fulfillment of a prescription drug), while theinternal pharmacy order processing device 114 may have greaterfunctionality (e.g., as operated by a pharmacist).

The order processing device 114 may track the prescription order as itis fulfilled by the pharmacy fulfillment device 112. The prescriptionorder may include one or more than one prescription drugs to be filledby the pharmacy. The order processing device 114 may make pharmacyrouting decisions and/or order consolidation decisions for theparticular prescription order. The pharmacy routing decisions includewhat device(s) in the pharmacy are responsible for filling or otherwisehandling certain portions of the prescription order. The orderconsolidation decisions include whether portions of one prescriptionorder or multiple prescription orders should be shipped together for apatient or a patient family. The order processing device 114 may alsotrack and/or schedule literature or paperwork associated with eachprescription order or multiple prescription orders that are beingshipped together.

The pharmacy management device 116 may enable and/or facilitatemanagement and operations in a pharmacy. For example, the pharmacymanagement device 116 may provide functionality to enable receipt andprocessing of prescription drug claims, management of pharmacypersonnel, management of pharmaceutical and non-pharmaceutical products,track products in the pharmacy, record workplace incidents involvepersonnel and products, and the like. In some embodiments, the orderprocessing device 114 may operate in combination with the pharmacymanagement device 116.

In some embodiments, the pharmacy management device 116 may be a deviceassociated with a retail pharmacy location (e.g., an exclusive pharmacylocation, a grocery store with a retail pharmacy, or a general salesstore with a retail pharmacy) or other type of pharmacy location atwhich a member attempts to obtain a prescription. The pharmacymanagement device 116 may be utilized by the pharmacy to submit theclaim to the PBM (e.g., through the benefit management device 102) foradjudication.

In some embodiments, the pharmacy management device 116 may enableinformation exchange between the pharmacy and the PBM, for example, toallow the sharing of member information such as drug history, and thelike, that may allow the pharmacy to better service a member (e.g., byproviding more informed therapy consultation and drug interactioninformation, etc.). In some embodiments, the benefit manager 102 maytrack prescription drug fulfillment and/or other information forpatients that are not members or have not identified themselves asmembers, at the time (or in conjunction with the time) in which theyseek to have a prescription filled at a pharmacy.

The pharmacy fulfillment devices 112, the order processing device 114,and/or the pharmacy management device 116 may include circuitry, aprocessor, a memory to store data and instructions, and communicationfunctionality. These devices 112-116, in some embodiments, are dedicatedto performing processes, methods and/or instructions described herein.Other types of electronic devices specifically configured to implementwith the processes, methods and/or instructions described herein mayalso be used.

In some embodiments, at least some functionality of the order processingdevice 114 may be included in the pharmacy management device 116. Theorder processing device 114 may be in a client-server relationship withthe pharmacy management device 116, in a peer-to-peer relationship withthe pharmacy management device 116, or in a different type ofrelationship with the pharmacy management device 116. The orderprocessing device 114 and/or the pharmacy management device 116 maycommunicate directly (e.g., by utilizing a local storage) and/or throughthe network 104 (e.g., by utilizing a cloud configuration or software asa service. etc.) with the storage 110.

The user device 108 is used by a device operator. The device operatormay be a user (e.g., an employee, a contractor, a benefit member, apatient of the pharmacy, or the like) associated with the system 100.Other device operators may also operate the user device 108. In someembodiments, the user device 108 may enable the device operator toattend to pharmacy operations in a convenient manner (e.g., remote froma pharmacy). In some embodiments, the user device 108 may enable thedevice operator to receive information about pharmacy processes,prescription drug fulfillment status, and the like.

The user device 108 may be a stand-alone device that solely provides atleast some of the functionality of the methods and systems, or may be amulti-use device that has functionality outside of analysis of themethods and systems. Examples of the user device 108 include a set-topbox (STB), a receiver card, a mobile telephone, a personal digitalassistant (PDA), a display device, a portable gaming unit, a computingsystem, and the like. Other devices, however, may also be used. In someembodiments, the computing system may include a mobile computing device.For example, the user device 108 may include a mobile electronic device,such an iPhone or iPad by Apple, Inc., mobile electronic devices poweredby Android by Google, Inc., and a Blackberry by Research In MotionLimited. The user device 108 may also include other computing devices,such as desktop computing devices, notebook computing devices, netbookcomputing devices, gaming devices, and the like. Other types ofelectronic devices may also be used.

The storage device 110 may include: a non-transitory storage (e.g.,memory, hard disk, CD-ROM, and the like) in communication with thebenefit manager device 102, the pharmacy device 106, and/or the userdevice 108 directly and/or over the network 104. The non-transitorystorage may store order data 118, member 120, claims data 122, drug data124, prescription data 126, and/or plan sponsor 128. Further, the system100 may include additional devices, which may communicate with eachother directly or over the network 104.

The order data 118 may be related to a prescription order. The orderdata may include the type of the prescription drug (e.g., drug name andstrength) and quantity of the prescription drug. The order data 118 mayalso include data used for completion of the prescription, such asprescription materials and/or the type and/or size of container in whichthe drug is dispended or in which is requested to be dispensed. Ingeneral, prescription materials include an electronic copy ofinformation regarding the prescription drug for inclusion with orotherwise provided (e.g., via email) in conjunction with the fulfilledprescription. The prescription materials may include electronicinformation regarding drug interaction warnings, recommended usage,possible side effects, expiration date, date of prescribing, or thelike. The order data 118 may be used by the pharmacy to fulfill apharmacy order.

In some embodiments, the order data 118 includes verificationinformation associated with fulfillment of the prescription in thepharmacy. For example, the order data 118 may include videos and/orimages taken of (i) the prescription drug prior to dispensing, duringdispensing, and/or after dispensing, (ii) the prescription container(e.g., a prescription bottle and sealing lid, prescription packaging,and the like) used to contain the prescription drug prior to dispensing,during dispensing, and/or after dispensing, (iii) the packaging and/orpackaging materials used to ship or otherwise deliver the prescriptiondrug prior to dispensing, during dispensing, and/or after dispensing,and/or (iv) the fulfillment process within the pharmacy. Other type ofverification information such as bar code data read from pallets, bins,trays, carts, and the like used to facilitate transportation ofprescriptions within the pharmacy may also be stored as order data 118.

The member data 120 includes information regarding the membersassociated with the PBM. The information stored as member data 120 mayinclude personal information, personal health information, protectedhealth information, fitness data, health data, web and mobile appactivity, and the like. Examples of the member data 120 include name,address, telephone number, e-mail address, prescription drug history,and the like. The member data 120 may include a plan sponsor identifierthat identifies the plan sponsor associated with the member and/or amember identifier that identifies the member to the plan sponsor. Themember data 120 may also include, by way of example, dispensationpreferences such as type of label, type of cap, message preferences,language preferences, or the like.

The member data 120 may be accessed by various devices in the pharmacyto obtain information utilized for fulfillment and shipping ofprescription orders. In some embodiments, an external order processingdevice 114 operated by or on behalf of a member may have access to atleast a portion of the member data 120 for review, verification, orother purposes.

In some embodiments, the member data 120 may include information forpersons who are patients of the pharmacy but are not members in apharmacy benefit plan being provided by PBM. For example, these patientsmay obtain drug directly from the pharmacy, through a private labelservice offered by the pharmacy, or otherwise. In general, the use ofthe terms member (e.g., of a prescription drug benefit plan) and patient(e.g., of a pharmacy) may be used interchangeably in this disclosure.

The claims data 122 includes information regarding pharmacy claimsadjudicated by the PBM under a drug benefit program provided by the PBMfor one, or more than one, plan sponsors. In general, the claims data122 includes an identification of the client that sponsors the drugbenefit program under which the claim is made, and/or the member thatpurchased the prescription drug giving rise to the claim, theprescription drug that was filled by the pharmacy (e.g., the nationaldrug code number), the dispensing date, generic indicator, GPI number,medication class, the cost of the prescription drug provided under thedrug benefit program, the copay/coinsurance amount, rebate information,and/or member eligibility, and the like. Additional information may beincluded.

In some embodiments, other types of claims beyond prescription drugclaims may be stored in the claims data 122. For example, medicalclaims, dental claims, wellness claims, or other type of healthcare-related claims for members may be stored as a portion of the claimsdata 122.

In some embodiments, the claims data 122 includes claims that identifythe members with whom the claims are associated. In some embodiments,the claims data 122 includes claims that have been de-identified (e.g.,associated with a unique identifier but not with a particular,identifiable member), aggregated, and/or otherwise processed.

The drug data 124 may include drug name (e.g., technical name and/orcommon name), other names by which the drug is known by, activeingredients, an image of the drug (e.g., in pill form), and the like.The drug data 124 may include information associated with a singlemedication or multiple medications.

The prescription data 126 may include information regardingprescriptions that may be issued by prescribers on behalf of patients,who may be members of the pharmacy benefit plan, for example to befilled by a pharmacy. Examples of the prescription data 126 includepatient names, medication or treatment (such as lab tests), dosinginformation, and the like. The prescriptions may be electronicprescriptions, paper prescriptions that have been scanned, or otherwise.In some embodiments, the dosing information reflects a frequency of use(e.g., once a day, twice a day, before each meal, etc.) and a durationof use (e.g., a few days, a week, a few weeks, a month, etc.).

In some embodiments, the order data 118 may be linked to associatedmember data 120, claims data 122, drug data 124, and/or prescriptiondata 126.

The plan sponsor data 128 includes information regarding the plansponsors of the PBM. Examples of the plan sponsor data 128 includecompany name, company address, contact name, contact telephone number,contact e-mail address, and the like.

FIG. 2 illustrates the pharmacy fulfillment device 112, according to anexample embodiment. The pharmacy fulfillment device 112 may be used toprocess and fulfill prescriptions and prescription orders. Afterfulfillment, the fulfilled prescriptions are packed for shipping.

The pharmacy fulfillment device 112 may include devices in communicationwith the benefit manager device 102, the order processing device 114,and/or the non-transitory storage 110, directly or over the network 104.Specifically, the pharmacy fulfillment device 112 may include palletsizing and pucking device(s) 206; loading device(s) 208; inspectdevice(s) 210, unit of use device(s) 212, automated dispensing device(s)214, manual fulfillment device(s) 214, review device(s) 218, imagingdevice(s) 220, cap device(s) 222, accumulation device(s) 224, literaturedevice(s) 228, packing device(s) 226, and unit of use packing device(s)230. Further, the pharmacy fulfillment device 112 may include additionaldevices, which may communicate with each other directly or over thenetwork 104.

In some embodiments, operations performed by one or more of thesedevices 206-230 may be performed sequentially, or in parallel with theoperations of devices as may be coordinated by the order processingdevice 114. In some embodiments, the order processing device 114 tracksa prescription with the pharmacy based on operations performed by one ormore than one of the devices 206-230.

In some embodiments, the pharmacy fulfillment device 112 may transportprescription drug containers, for example, between more than one of thedevices 206-230 in the high volume fulfillment center, by use ofpallets. The pallet sizing and pucking device 206 may configure pucks ina pallet. A pallet may be a transport structure for a number ofprescription containers, and may include a number of cavities. A puckmay be placed in one or more than one of the cavities in a pallet by thepallet sizing and pucking device 206. The puck may include a receptaclesized and shaped to receive a prescription container. Such containersmay be supported by the pucks during carriage in the pallet. Differentpucks may have differently sized and shaped receptacles to accommodatecontainers of differing sizes, as may be appropriate for differentprescriptions.

The arrangement of pucks in a pallet may be determined by the orderprocessing device 114 based on prescriptions that the order processingdevice 114 decides to launch. The arrangement logic may be implementeddirectly in the pallet sizing and pucking device 206. Once aprescription is set to be launched, a puck suitable for the appropriatesize of container for that prescription may be positioned in a pallet bya robotic arm or pickers. The pallet sizing and pucking device 206 maylaunch a pallet once pucks have been configured in the pallet.

The loading device 208 may load prescription containers into the puckson a pallet by a robotic arm, a pick and place mechanism, or the like.In one embodiment, the loading device 208 has robotic arms or pickers tograsp a prescription container and move it to and from a pallet or toand from a puck. The loading device 208 may also print a label that isappropriate for a container that is to be loaded onto the pallet, andapply the label to the container. The pallet may be located on aconveyor assembly during these operations (e.g., at the high volumefulfillment center or the like).

The inspect device 210 may verify that containers in a pallet arecorrectly labeled and in the correct spot on the pallet. The inspectdevice 210 may scan the label on one or more than one container on thepallet. Labels of containers may be scanned or imaged in full or in partby the inspect device 210. Such imaging may occur after the containerhas been lifted out of its puck by a robotic arm, picker, or the like,or may be otherwise scanned or imaged while retained in the puck. Insome embodiments, images and/or video captured by the inspect device 210may be stored in the storage device 110 as a portion of the order data118.

The unit of use device 212 may temporarily store, monitor, label and/ordispense unit of use products. In general, unit of use products areprescription drug products that may be delivered to a patient or memberwithout being repackaged at the pharmacy. These products may includepills in a container, pills in a blister pack, inhalers, liquids in aspray or other dispensing container, and the like. Prescription drugproducts dispensed by the unit of use device 212 may be packagedindividually or collectively for shipping, or may be shipped incombination with other prescription drugs dispensed by other devices(e.g., in the high volume fulfillment center).

At least some of the operations of devices 206-230 may be directed bythe order processing device 114. For example, the manual fulfillmentdevice 216, the review device 218, the automated dispensing device 214,the packing device 226, and/or another device may receive instructionsprovided by the order processing device 114.

The automated dispensing device 214 may include one or more than onedevices that dispense prescription drugs or pharmaceuticals intoprescription containers in accordance with one or multiple prescriptionorders. In general, the automated dispensing device 214 may includemechanical and electronic components with, in some embodiments, softwareand/or logic to facilitate pharmaceutical dispensing that wouldotherwise be performed in a manual fashion by a pharmacist and/orpharmacist technician. For example, the automated dispensing device 214may include high volume fillers that fill a number of prescription drugtypes at a rapid rate and blister pack machines that dispense and packdrugs into a blister pack. Prescription drugs dispensed by the automateddispensing devices 214 may be packaged individually or collectively forshipping, or may be shipped in combination with other prescription drugsdispensed by other devices in the high volume fulfillment center.

The manual fulfillment device 216 may provide for manual fulfillment ofprescriptions. For example, the manual fulfillment device 216 mayreceive or obtain a container and enable fulfillment of the container bya pharmacist or pharmacy technician. In some embodiments, the manualfulfillment device 216 provides the filled container to another devicein the pharmacy fulfillment devices 112 to be joined with othercontainers in a prescription order for a patient or member. In general,a manual fulfillment may include operations at least partially performedby a pharmacist or a pharmacy technician. For example, a person mayretrieve a supply of the prescribed drug, may make an observation, maycount out a prescribed quantity of drugs and place them into aprescription container, or the like. Some portions of the manualfulfillment process may be automated by use of a machine. For example,counting of capsules, tablets, or pills may be at least partiallyautomated (e.g., through use of a pill counter or the like).Prescription drugs dispensed by the manual fulfillment device 216 may bepackaged individually or collectively for shipping, or may be shipped incombination with other prescription drugs dispensed by other devices inthe high volume fulfillment center.

The review device 218 may process prescription containers to be reviewedby a pharmacist for proper pill count, exception handling, prescriptionverification, and the like. Fulfilled prescriptions may be manuallyreviewed and/or verified by a pharmacist, as may be required by state orlocal law. A pharmacist or other licensed pharmacy person who maydispense certain drugs in compliance with local and/or other laws mayoperate the review device 218 and visually inspect a prescriptioncontainer that has been filled with a prescription drug. The pharmacistmay review, verify, and/or evaluate drug quantity, drug strength, and/ordrug interaction concerns, or otherwise perform pharmacist services. Thepharmacist may also handle containers which have been flagged as anexception, such as containers with unreadable labels, containers forwhich the associated prescription order has been cancelled, containerswith defects, and the like. In an example embodiment, the manual reviewmay be performed at the manual station.

The imaging device 220 may image containers prior to filling and/orafter they have been filled with pharmaceuticals. The imaging device 220may measure a fill height of the pharmaceuticals in the container basedon the obtained image to determine if the container is filled to thecorrect height given the type of pharmaceutical and the number of pillsin the prescription. Images of the pills in the container may also beobtained to detect the size of the pills themselves and markingsthereon. The images may be transmitted to the order processing device114, and/or stored in the storage device 110 as part of the order data118.

The cap device 222 may be used to cap or otherwise seal a prescriptioncontainer. In some embodiments, the cap device 222 may secure aprescription container with a type of cap in accordance with a patientpreference (e.g., a preference regarding child resistance, a preferenceregarding built-in adherence functionality, or the like), a plan sponsorpreference, a prescriber preference, or the like. The cap device 222 mayalso etch a message into the cap or otherwise associate a message intothe cap, although this process may be performed by a different device inthe high volume fulfillment center.

The accumulation device 224 accumulates various containers ofprescription drugs in a prescription order. The accumulation device 224may accumulate prescription containers from various devices or areas ofthe pharmacy. For example, the accumulation device 224 may accumulateprescription containers from the unit of use device 212, the automateddispensing device 214, the manual fulfillment device 216, and the reviewdevice 218, at the high volume fulfillment center. The accumulationdevice 224 may be used to group the prescription containers prior toshipment to the member or otherwise.

The literature device 228 prints, or otherwise generates, literature toinclude with prescription drug orders. The literature may be printed onmultiple sheets of substrates, such as paper, coated paper, printablepolymers, or combinations thereof. The literature printed by theliterature device 228 may include information required to accompany theprescription drugs included in a prescription order, relating toprescription drugs in the order, financial information associated withthe order (e.g., an invoice or an account statement, or the like).

In some embodiments, the literature device 228 folds or otherwiseprepares the literature for inclusion with a prescription drug order(e.g., in a shipping container or the like). In some embodiments, theliterature device 228 that prints the literature may be separate fromthe literature device that prepares the literature for inclusion with aprescription order.

The packing device 226 packages a prescription order in preparation forshipping the order. The packing device 226 may box, bag, or otherwisepackage the fulfilled prescription order for delivery. The packingdevice 226 may further place inserts, (e.g., literature or otherpapers), into the packaging received from the literature device 228 orotherwise. For example, bulk prescription orders may be shipped in abox, while other prescription orders may be shipped in a bag which maybe a wrap seal bag. The packing device 226 may label the box or bag withan address and a recipient's name. The label may be printed and affixedto the bag or box, be printed directly onto the bag or box, or otherwiseassociated with the bag or box. The packing device 226 may sort the boxor bag for mailing in an efficient manner (e.g., sort by deliveryaddress, sort by zip code, or the like). The packing device 226 mayinclude ice or temperature sensitive elements for prescriptions whichare to be kept within a temperature range during shipping in order toretain efficacy or otherwise. The ultimate package may then be shippedthrough postal mail, through a mail order delivery service that shipsvia ground and/or air (e.g., UPS, FEDEX, or DHL, or the like), throughdelivery service, through a local delivery service (e.g., a courierservice), through a locker box at a shipping site (e.g., an AMAZONlocker, library locker, a post office box, or the like), or otherwise.

The unit of use packing device 230 packages a unit of use prescriptionorder in preparation for shipping the order. The unit of use packingdevice 230 may include manual scanning of containers to be bagged forshipping to verify each container in the order. In an exampleembodiment, the manual scanning may be performed at a manual station.

The pharmacy fulfillment device 112 in FIG. may include single devices206-230 or multiple devices 206-230 (e.g., depending upon implementationin a pharmacy). The devices 206-230 may be the same type or model ofdevice or may be different device types or models. When multiple devicesare present, the multiple devices may be of the same device type ormodels or may be a different device type or model. The types of devices206-230 shown in FIG. 2 are example devices. In other configurations ofthe system 100, lesser, additional, or different types of devices may beincluded.

Moreover, multiple devices may share processing and/or memory resources.The devices 206-230 may be located in the same area or in differentlocations. For example, the devices 206-230 may be located in a buildingor set of adjoining buildings. The devices 206-230 may be interconnected(e.g., by conveyors), networked, and/or otherwise in contact with oneanother or integrated with one another (e.g., at the high volumefulfillment center). In addition, the functionality of a device may besplit among a number of discrete devices and/or combined with otherdevices.

FIG. 3 illustrates a bottle 302 that may be utilized by a pharmacy forfulfillment of a prescription order and that may be accumulated by theaccumulation device 224. The bottle 302 is generally cylindrical with anopen interior and may be of one or a variety of sizes utilized by apharmacy for fulfillment of a prescription. For example, a pharmacy mayhave two different sized bottles or three different sized bottles. Anynumber of different sized bottles 302 may be used. Different sizedbottles may be further described, for example, as having differingvolumes, differing diameters, and/or differing heights. Shapes otherthan cylindrical shapes may be used for the bottles 302. Examples ofother shapes include regular prisms, elliptical cylinders, andcombinations thereof. The bottles 302 may include labels 304. A label304 may be uniquely printed for each bottle 302 (e.g., to includeinformation such as a patient name, drug name, dosage, directions foruse, and/or other information required and/or desirable for aprescription label). The labels 304, or some portion of the informationfor the labels 304, may be the same for a particular set of the labels304, such as the dispensing pharmacy. Although the accumulation device224 is generally described as being utilized to accumulate bottles, insome embodiments, other suitable containers may be accumulated by anaccumulation device 224.

FIG. 4 illustrates an accumulation device 224, according to an exampleembodiment. The accumulation device 224 may be deployed in the system100 of FIG. 1, or may otherwise be used. The accumulation device 224 mayinclude a control subsystem 402 and an accumulation subsystem 404. Thecontrol subsystem 402 may include a single module or multiple modulesand enables the automated dispensing device 214 to control theaccumulation subsystem 404, while the accumulation subsystem 404 mayinclude a single or multiple devices and enables the accumulation device224 with accumulation operations (e.g., accumulating containers ofprescription drugs in an individual prescription order).

An example deployment of the accumulation device 224 is within thesystem 100. In such a deployment, the system 100 includes a singleconveyor or multiple conveyors, robotic transport systems or otherdevices to facilitate transporting containers or pallets of containers302 through mechanical devices within the system 100, such as devices tolabel, fill, cap, and check containers. The accumulation device 224 maybe otherwise deployed.

The accumulation device 224 may be deployed to accumulate multipleprescription bottles 302 in a prescription order. One or more of thesteps of labeling, filling, capping or checking one or more of thebottles 302 in the prescription order may be delayed relative to one ormore than one of the steps of labeling, filling, capping or checking foranother one or more of the containers in the same prescription order.The accumulation device 224 may store the bottles 302 while othercontainers are processed. The accumulation device 224 may be deployed toreintroduce a prescription bottle 302 into a portion of the system 100,e.g., via one or more conveyors, which is in communication with devicesconfigured to pack and ship the prescription order that is or includesthe prescription bottle 302. Devices configured to pack and ship theprescription order may include the packing device(s) 226, 230. Forexample, a prescription container 302 reviewed pursuant to qualityassurance processes (e.g., using the review device 218) may betransported to the accumulation subsystem 404 of the accumulation device224 for further processing. The accumulation device 224 may be deployedto retain one or more than one prescription bottle 302 of a prescriptionorder until other components of the prescription order, such asprescription drug products dispensed by the unit of use device 230, theautomated dispensing device 214, and/or the manual fulfillment device216 have been selected or prepared for the prescription order. In anexample embodiment, the accumulation device 224 is deployed for at leastall of the foregoing purposes. In another example embodiment, theaccumulation device 224 is deployed for fewer than all of the foregoingpurposes. In yet another example embodiment, the accumulation device 224is deployed to retain one or more than one bottle 302 of a prescriptionorder during any period in which there is not a complete path throughthe system 100 to package and ship the entire prescription order. Inanother embodiment, the accumulation device 224 is deployed to retainone or more than one bottle 302 of a prescription order while anotherorder component is reviewed for quality assurance or prescriptionverification purposes, either at a review device 218 or otherwise withinthe system 100.

FIGS. 5-8 illustrate the accumulation subsystem 404, according to anexample embodiment. The accumulation subsystem 404 may be deployedwithin the accumulation device 224, or may otherwise be deployed. Theaccumulation subsystem 404 enables accumulation of multiple bottles 302of prescription drugs in an automatic or semiautomatic manner. Forexample, the accumulation subsystem 404 may accumulate prescriptionbottles 302 from any one or more of the unit of use device 210, theautomated dispensing device 212, the manual fulfillment device 216, andthe review device 218. The accumulation subsystem 404 may accumulate oneor more prescription bottles 302 for subsequent quality assurancevalidation or prescription verification or validation, or while one ormore other order component of the prescription order is undergoingquality assurance validation or prescription verification or validation.The accumulation subsystem 404 may accumulate multiple prescriptionbottles 302 from a single device, such as the manual fulfillment device216 or the review device 218. In reference to a particular prescriptionorder, the accumulation subsystem 404 may accumulate multipleprescription bottles 302 corresponding to that prescription order withinthe accumulation subsystem 404. In some embodiments, the accumulationsubsystem 404 may temporarily store a single or multiple prescriptionbottles 302 corresponding to that prescription order during all or aportion of a period in which other portions of that prescription orderare being fulfilled, checked, or otherwise processed elsewhere in thesystem 100, for example, by the unit of use device 212.

The accumulation subsystem 404 illustrated in FIGS. 5-8 includes a frame502, a bottle scan and pick assembly 602, an upper gantry 504, a lowergantry 506, a table assembly 508, a bottle escapement assembly 510, 512and a reject bin assembly 514.

The frame 502 provides support for one or more devices of theaccumulation subsystem 404, such as a bottle scan and pick assembly 602,an upper gantry 504, a lower gantry 506, a table assembly 508, bottleescapement assemblies 510, 512, and a reject bin assembly 514. Althoughtwo bottle escapement assemblies 510, 512 are illustrated in theembodiment of the accumulation subsystem 404 of FIG. 5, in otherembodiments, the accumulation subsystem 404 may have only one bottleescapement assembly or may have more than two bottle escapementassemblies.

The bottles 302 may be transported to the bottle scan and pick assembly602 via an entry conveyor 604. The entry conveyor 604 may be a beltconveyor or a chain conveyor; however, other types of conveyors may beused for the entry conveyor 604. As described in further detail below,the bottle scan and pick assembly 602 may include a rotary assembly 606configured to receive bottles 302. The rotary assembly 606 may rotate toplace the bottles 302 in a pick position. The bottle scan and pickassembly 602 may include a gripper assembly 516 that is configured togrip the bottle 302 in the pick position.

The gripper assembly 516 may be in communication with the upper gantry504. The upper gantry 504 may facilitate movement of the gripperassembly 516 along x, y and z axis above the table assembly 508. In anexample embodiment, the upper gantry 504 is or includes x, y and z Boschlinear actuators. Other embodiments of gantries may be deployed as theupper gantry 504 in the accumulation subsystem 404.

The table assembly 508 includes multiple holding tubes configured toreceive bottles 302, such as holding tube 518. The upper gantry 504, incombination with the gripper assembly 516, may be deployed to select thebottle 302 from the pick position of the rotary assembly 606, lift thebottle 302 out of the rotary assembly 606, move the bottle to a positionover a holding tube, such as the holding tube 518, and release thebottle into the holding tube 518. It should be appreciated that inanother embodiment of a table assembly, in lieu of holding tubes, anumber of rods could be deployed to form points of points of contactaround the perimeter of a bottle to retain bottles within the table. Therods could be otherwise configured to perform the functions of theholding tubes, as described herein.

The lower gantry 506 facilitates movement of an unload assembly 702along x, y and z axis beneath the holding tubes, such as holding tube518, of the table assembly 508 and over the bottle escapement assemblies510, 512. In an example embodiment, the lower gantry 506 is or includesx, y and z Bosch linear actuators. Other embodiments of gantries may bedeployed as the lower gantry 506 in the accumulation subsystem 404. Thelower gantry 506 is described in further detail below.

As described in further detail below, the unload assembly 702 may beconfigured to release bottles 302 from the holding tube 518 such thatthe bottle(s) 302 held in the holding tube 518 are received by an unloadassembly tube 704. The unload assembly 702 may be further configured toempty bottle(s) 302 from the unload assembly tube 704 into the bottleescapement assemblies 510, 512.

The accumulated or temporarily stored bottle(s) 302 deposited into thebottle escapement assemblies 510, 512 may pass through and exit thebottle escapement assemblies 510, 512, onto exit conveyor 520. The exitconveyor 520 may transport the accumulated bottles 302 out of theaccumulation system 304 to other devices within the system 100, forexample to the literature device(s) 228 or the packing device(s) 226,230.

FIGS. 9 and 10 illustrate the rotary assembly 606 of the bottle scan andpick assembly 602, according to an example embodiment. The rotaryassembly 606 may include a rotary wheel 902 and may be configured toreceive and singulate bottles 302 upon entering the accumulationsubsystem 404. As described in further detail below, the rotary wheel902 may rotate among positions in which a bottle 302 is accepted fromthe entry conveyor 604, in which a bottle is spun by a wrap wheel whilea scanner reads a bar code on the label 304 of the bottle 302, and inwhich a bottle 302 is picked by gripper assembly 516. The rotary wheel902 may have a low durometer setting to allow the bottle 302 to spinwithin pockets of the rotary wheel 902 without damaging the label 304.

A rotary assembly motor 1001 actuates the rotary wheel 902. The rotaryassembly motor 1001 may be a Rockwell Automation Kinetix VP series lowinertia servo motor. Other types of motors may be used for the rotaryassembly motor 1001, such as other servo motors or other motors thatprovide for repeatability of positioning.

The rotary wheel 902 includes pockets 906, 908, 910 configured toreceive bottles 302 a, 302 b, 302 c via the entry conveyor 604. A bottleserpentine assembly 912 may be provided, wherein the bottle serpentineassembly 912 is configured to relieve back pressure among the bottles302 a, 302 b, 302 c prior to entry into the pockets 906, 908, 910 of therotary wheel 902 from the entry conveyor 604. Although the rotary wheel902 of the embodiment of the rotary assembly 606 illustrated in FIGS. 9and 10 includes three pockets 906, 908, 910, in other embodiments, feweror more than three pockets may be provided in the rotary wheel 902 ofthe rotary assembly 606.

After the bottle 302 has been transported into a pocket 906, 908, 910via the entry conveyor 604 and the bottle serpentine assembly 912, therotary assembly motor 1001 may actuate the rotary wheel 902, causing itto rotate (e.g., clockwise or counterclockwise). In the embodimentillustrated in FIGS. 9 and 10, the rotary wheel 902 will turncounterclockwise. The pockets 906, 908, 910 may include bearings or freewheels to allow the bottles 302 a, 302 b, 302 c to rotate withoutdamaging the label 304 on the bottles 302 a, 302 b, 302 c.

When the bottle 302 b is in the pocket 906, 908, 910 at the position ofthe pocket 908 on FIG. 9, a wrap wheel 914, actuated by a wrap wheelmotor 1002, connected to a belt 1006 and a spring loaded belt shaft1008, may spin the bottle 302 within the pocket 908. A scanner 1004attached to the rotary assembly 606 may be configured to read the label304 when the bottle 302 is spun by the wrap wheel 914. The spring loadedbelt shaft 1008 may accommodate different sized bottles 302 within thepocket 908.

In an example embodiment, the wrap wheel motor 1002 is brushless motor.In a particular embodiment, the wrap wheel motor 1002 is a BLH seriesbrushless motor from Oriental Motor U.S.A. Corp. Other types of motorsmay be used for the wrap wheel motor 1002. In an example embodiment, thescanner 1004 is a Microscan Systems, Inc. Mini Hawk Xi imager. Othertypes of imagers may be used as the scanner 1004.

The reading of the label 304 enables association of the bottle 302 bwith a particular prescription order and holding tube (such as theholding tube 518) within the table assembly 508. After the label 304 ofthe bottle 302 has been read by the scanner 1004, the rotary assemblymotor 1001 may actuate the rotary wheel 902, causing it to turn to theposition of the pocket 910 on FIG. 9. The position of pocket 910 on FIG.9 may be the pick position from which the bottle 302 is removed from therotary wheel 902 by the gripper assembly 516. Sensor 916 may be attachedto the rotary assembly 606 in a position above the rotary wheel 902 andconfigured to detect the removal of the bottle 302 from the rotary wheel902 by the gripper assembly 516. After the bottle 302 has been removedfrom the rotary wheel 902, the rotary assembly motor 1001 may actuatethe rotary wheel 902, causing it to turn (e.g., clockwise orcounterclockwise), enabling another bottle 302 to be received within thenow empty pocket 906, 908, 910 of the rotary wheel 902.

If the reading of the label 304 by the scanner 1004 fails to causeassociation of the bottle 302 with a particular prescription order, orif no label is detected by the scanner 1004, the bottle 302 may beselected from the pick position by the gripper assembly 516 and releasedinto the reject bin assembly 514. For example, the bottle 302 may bereleased into a tube of the reject bin assembly 514 that is disposedamong the holding tubes of the table assembly 508.

FIG. 11 illustrates the upper gantry 504 according to an exampleembodiment and FIG. 12 illustrates the lower gantry 506 according to anexample embodiment. Each of the gantries 504, 506 includes an x-axisassembly 1102, 1202, a y-axis assembly 1104, 1204 and a z-axis assembly1106, 1206. As noted above, and as described in further detail below,the gripper assembly 516 may be attached to the z-axis assembly 1106 ofthe upper gantry 504 and the unload assembly 702 may be attached to thez-axis assembly 1206 of the lower gantry 506.

Each x-axis assembly 1102, 1202 includes x-axis belted rails 1108, 1110,1208, 1210. The x-axis belted rails 1108, 1110 of the upper gantry 504are connected to one another by a connecting shaft 1112. Each x-axisassembly 1102, 1202 includes an x-axis gantry motor 1114, 1212configured to power the x-axis belted rails 1108, 1110, 1208, 1210 andactuate the x-axis movement of the gripper assembly 516 or the unloadassembly 702, as the case may be, via the upper or lower gantry, 504,506, as the case may be. The x-axis belted rails 1108, 1110, 1208, 1210include slides 1116, 1214 to connect the y-axis assemblies 1104, 1204 tothe x-axis assemblies 1102, 1202 of the upper and lower gantries 504,506, respectively.

Each y-axis assembly 1104, 1204 includes y-axis belted rails 1118, 1120,1216, 1218. Each y-axis assembly 1104, 1204 includes a y-axis gantrymotors 1122, 1220 configured to power the y-axis belted rails 1118,1120, 1216, 1218 and actuate the y-axis movement of the gripper assembly516 or the unload assembly 702, as the case may be, via the upper orlower gantry, 504, 506, as the case may be. The y-axis belted rails1118, 1216 include slides 1124, 1222 to connect the y-axis assemblies1104, 1204 to the z-axis assemblies 1106, 1206 of the upper and lowergantries 504, 506, respectively.

The z-axis assemblies 1106, 1206 facilitate the z-axis movement of thegripper assembly 516 and the unload assembly 702, respectively, via theupper and lower gantries, 504, 506, respectively, wherein the z-axismovement may be actuated by a motor. The z-axis assemblies 1106, 1206 incombination with the gripper assembly 516 and the unload assembly 702,respectively, are described in further detail below, in reference toFIGS. 18 and 19 and 21 and 22, respectively.

Cable guides 1126, 1128, 1130, 1224, 1226 protect cables used to controlthe movement of the upper and lower gantries 504, 506, e.g., viainstructions provided by the control subsystem 402.

The x-axis gantry motors 1114, 1212 and the y-axis gantry motors 1122,1220 may be servo motors. In an example embodiment, the gantry motors1114, 1212, 1122, 1220 are Rockwell Automation Kinetix VP series lowinertia servo motor. Other types of motors that have similar rates andtorques, sufficient to move the equipment at a selected cycle rate andtime, may be used for the gantry motors 1114, 1212, 1122, 1220.

FIGS. 13-17 illustrate a table assembly 508, or portions thereof,according to an example embodiment. The table assembly 508 may bedeployed in the accumulation subsystem 404, or may otherwise bedeployed.

The table assembly 508 includes multiple holding tubes, including theholding tubes 518 a, 518 b, 518 c, 518 d, which are supported by asupport structure 1302. The support structure includes a base plate 1304and an upper plate 1306.

The holding tubes 518 a, 518 b, 518 c, 518 d, may be arranged in a tubecluster 1502. The tube cluster 1502 may include a catch assembly 1402affixed to the bottom of the holding tubes 518 a, 518 b, 518 c, 518 d inthe tube cluster 1502. The catch assembly 1402 may include movable catchassembly fingers 1504 a, 1504 b, 1504 c. Catch assembly fingers 1504 a,1504 b, 1504 c, when open, may obstruct the lower opening of the holdingtubes 518 a, 518 b, 518 c, 518 d and, thereby, operate to retain thebottles 302 in the holding tubes 518 a, 518 b, 518 c, 518 d,respectively, of the tube cluster 1502. For example, in FIG. 15, catchassembly fingers 1508 a, 1508 c are illustrated in an open, obstructingposition.

The catch assembly fingers 1504 a, 1504 b, 1504 c may be hinged suchthat a catch assembly finger, e.g., the catch assembly finger 1504 b,will move up into a finger slot 1506 upon engagement by the unloadassembly 702. The finger slot 1506 is sized such that the associatedcatch assembly finger is completely received therein. When the catchassembly finger 1504 b is released, bottles 302 held within the holdingtube 518 a will be released into the unload assembly tube 704 of theunload assembly 702.

The catch assembly fingers 1504 a, 1504 b, 1504 c may be weighted suchthat the tip is sufficiently heavy to cause the catch assembly fingers1504 a, 1504 b, 1504 c to fall back to an open, obstructing positionafter the unload assembly 702 is removed from the holding tube 518. Thatis, the catch assembly fingers 1504 a, 1504 b, 1504 c are biased intothe open, obstructing position. The catch assembly fingers 1504 a, 1504b, 1504 c may then be urged into the closed, un-obstructing position.The catch assembly finger 1504 a is illustrated in a position in whichit is beginning to fall back into the open, obstructing position, afterremoval of the unload assembly 702. For clarity, a close-up illustrationof the embodiment of the catch assembly 1402 of FIGS. 13-15 is providedas FIG. 16. In an example embodiment, the bottom of a catch assemblyfinger is disposed, in its open, obstructing position, at a positiveangle (e.g., above the horizontal plane that would include the top ofthe release tube at the point at which it engages the catch assemblyfinger) of between approximately 22 degrees and 25 degrees. When a catchassembly finger is disposed at a positive angle in this approximaterange, the catch assembly finger may lift the bottle without damaging itand fall back properly into the open, obstructing position after theunload assembly tube 704 has been removed from the holding tube 518.

FIG. 17 illustrates a cross section of the holding tubes 518 a, 518 d ofthe table assembly 508 of FIGS. 13-15. The holding tubes 518 are eachsized to hold more than one bottle 302. For example, the holding tube518 d is shown as holding four bottles 302 and the holding tube 518 a isshowing holding a single bottle 302. The catch assembly fingers 1504 b,1504 c of the catch assembly 1402 retain the bottles 302 within theholding tubes 518 a, 518 d. When deployed to accumulate pharmaceuticalbottles of a prescription order, all of the bottles 302 in the holdingtube 518 d are associated with a single prescription order. The bottle302 in the holding tube 518 a may be associated with the sameprescription order as the bottles 302 in the holding tube 518 d or itmay be associated with a different prescription order. Each holding tube518 a, 518 b, 518 c, 518 d is individually addressable by theaccumulation device 224.

In the embodiment of FIGS. 13-15, the tube cluster 1502 includes fourholding tubes 518 a, 518 b, 518 c, 518 d. In other embodiments, thequantity of holding tubes in a tube cluster may be greater than four orless than four. In an example embodiment, a tube cluster contains twoholding tubes; in another example embodiment, a tube cluster contains asingle holding tube; and in other example embodiments, a tube clustercontains more than four holding tubes. Each tube cluster 1502 isindividually addressable by the accumulation device 224. When anindividual prescription order consists of more than the number ofbottles 302 that can be held in a single holding tube 518, a tubecluster 1502 may be assigned to a single prescription order.

In an example embodiment, the table assembly 508 includes at least 100holding tubes, in another embodiment at least 250 tubes, in stillanother embodiment at least 400 holding tubes. In another exampleembodiment, the table assembly 508 includes at least 500 holding tubes.In yet another example embodiment, such as the embodiment illustrated inFIGS. 13-15, the table assembly 508 includes between 400 and 600 holdingtubes. In a further embodiment, the table assembly 508 includes fewerthan 400 holding tubes and, in another example embodiment, the tableassembly 508 includes more than 600 holding tubes. The number of holdingtubes may be based on the speed of the gantries in relation to bottleand order consolidation requirements.

In the embodiment of FIGS. 13-15, the holding tubes 518 a, 518 b, 518 c,518 d are generally cylindrical; in other embodiments, rods can be usedin place of holding tubes to hold bottles in the table assembly viapoints of contact around the bottles. The holding tubes 518 may beconfigured to receive a variety of sizes and/or shapes of bottles. Inother words, the bottles may have different dimensions. The holdingtubes 518 of some embodiments are configured to receive bottles 302having different diameters. For example, the holding tubes 518 of theembodiment of the table assembly 508 illustrated in FIGS. 13-15 areconfigured to receive cylindrical bottles ranging in sizes from adiameter of between approximately 1.7 and 1.8 inches (with a 75 ccvolume) to a diameter of between approximately 2.2 inches and 2.3 inches(with a 200 cc volume) and, when received by the holding tubes 518 a,518 b, 518 c, 518 d, a smaller size of bottle 302 may tilt, asillustrated with respect to the holding tube 518 a, but will not turn onits side, thus enabling the bottle 302 to exit the holding tube 518 aand, ultimately, the accumulation subsystem 404, in an upright position.In an example, the interior diameter of the holding tube 518 is slightlylarger than the largest bottle 302 that will be held within the holdingtube 518. For example, the interior diameter of the holding tube 518 maybe between approximately 5 percent and 6 percent larger than theexterior diameter of the largest bottle 302 that will be held within theholding tube.

In other embodiments, holding tubes may be configured to receive bottlesthat are smaller than approximately 1.7 inches in diameter or that arelarger than approximately 2.3 inches in diameter. In the embodiment ofFIGS. 13-15, the holding tubes 518 a, 518 b, 518 c, 518 d are configuredto receive up to four bottles 302. In other embodiments, holding tubesmay be configured to receive more than four bottles or fewer than fourbottles.

FIGS. 18 and 19 illustrate the gripper assembly 516 of the bottle scanand pick assembly 602, in combination with the z-axis assembly 1106 ofthe upper gantry 504, according to an example embodiment. The gripperassembly 516 includes gripper jaws 1802 configured to grip a bottle 302.For example, the gripper jaws 1802 may be configured to grip a varietyof sizes of caps, and at least the variety of sizes associated with thesizes of bottles 302 that will be retained in the accumulationsubsystem. The gripper jaws 1802 may have a knurled surface. The gripperassembly 516 may be a pneumatic gripper in which the opening function isachieved via air input and the gripping function is achieved via springsconfigured to close the gripper jaws 1102 upon release of the air. In anexample embodiment, the gripper assembly 516 is a pneumatic, PHD, Inc.Series GRT 3 jaw parallel gripper with a 40 mm bore, standard jawtravel, and proximity switches that is spring assist closed. Other typesof grippers may be used as the gripper assembly 516, such as aspring-loaded or servo-style gripper.

The gripper assembly 516 may be mounted to a z-axis belted rail 1804 ofthe z-axis assembly 1106. The z-axis assembly 1106 includes a z-axismotor 1806 configured to power the z-axis belted rail 1804 and actuatethe z-axis movement of the gripper assembly 516. The z-axis motor 1806may be a Rockwell Automation Kinetix VP series low inertia servo motor.In an example embodiment, the z-axis motor 1806 is the RockwellAutomation Kinetix VP low series inertia motor model number VPL-B0752.Other motors may be used as the z-axis motor 1806.

A bracket 1808 may be used to attach the z-axis assembly 1106 andgripper assembly 516 to the slide 1124 of the y-axis assembly 1104 ofthe upper gantry 504.

FIGS. 20 and 21 illustrate the unload assembly 702 according to anexample embodiment. The unload assembly 702 may be deployed in theaccumulation subsystem 404, or may otherwise be deployed.

The unload assembly 702 includes a cup 2002 disposed at the top of theunload assembly tube 704. When the unload assembly 702 is moved up intothe bottom of a holding tube, e.g., the holding tube 518 d of FIG. 17,via z-axis movement of the z-axis assembly 1206 of the lower gantry 506,the cup 2002 may enter the bottom of the holding tube 518 a and closethe catch assembly finger 1504 c into the unobstructed position, therebyreleasing the bottles 302 in the holding tube 518 d into the unloadassembly tube 704. The cup 2002 may be removable to facilitate ease ofreplacement and may be formed of a durable material to minimize weararising out of repeated engagement of the catch assembly fingers 1504 a,1504 b, 1504 c. In an example embodiment, the cup 2002 is formed fromsteel.

As shown in the embodiment of FIG. 21, an upper sensor 2004 isconfigured and positioned to detect bottle(s) 302 passing through theholding tube 518 into the unload assembly tube 704 after the catchassembly finger 1504 a, 1504 b, 1504 c has been released. A lower sensor2006 is configured and positioned to detect bottle(s) 302 passing fromthe unload assembly tube 704 into the lower escapement 510, 512.

If bottle(s) 302 are not detected by the upper sensor 2004, or if thebottles 302 are detected by the upper sensor 2004 but are not detectedby the lower sensor 2006, an alert may be generated, e.g., by thecontrol subsystem 402 of the accumulation device 224. An alert may beotherwise generated as a fault or jam condition.

A bottle release actuator 2008, affixed at or near the bottom of theunload assembly, actuates a bottle release rod 2102 that, when extended,as illustrated in FIG. 21, holds bottles 302 within the unload assemblytube 704 and, when retracted, releases the bottles 302 from the unloadassembly tube 704 into one of the bottle escapement assemblies 510, 512.In an example embodiment, the bottle release actuator 2008 is apneumatic cylinder. In a particular embodiment, the bottle releaseactuator 2008 is a Bimba Flat-I, double acting, pneumatic, single rodcylinder. Other embodiments of cylinders may be used as the bottlerelease actuator 2008, such as an electrically driven cylinder such as asolenoid or a cylinder with a full stroke design that includes fullrange of movement. The bottle release rod 2102 may have a ⅜ inchdiameter. The bottle release rod 2102 may be configured to extend onlywhen the lower sensor 2006 is clear or otherwise indicates that nobottle 302 is present in the extension path of the bottle release rod2102.

A bracket 2010 may be used to attach the z-axis assembly 1206 and unloadassembly 702 to the slide 1222 of the y-axis assembly 1204 of the lowergantry 506.

FIGS. 22 and 23 illustrate the bottle escapement assembly 510 accordingto an example embodiment. The bottle escapement assembly 510 includes anescapement tube 2202 to receive bottle(s) 302 released from the unloadassembly tube 704. An opening 2204 in the side of the escapement tube2202 is open to the conveyor 520. An escapement rod 2302 is positionedso that when it is extended as illustrated in FIG. 23, the escapementrod 2302 forces a bottle 302 out of the escapement tube 2202, throughthe opening 2204 and onto the conveyor 520. The escapement rod 2302 isthen retracted so that another bottle is allowed to drop to the bottomof the escapement tube 2202. The next bottle 302 is then pushed out ofthe opening 2204 onto the conveyor 520.

The escapement rod 2302 may include a c-shaped adaptor 2304 tofacilitate retaining the bottle 302 in an upright position as it ismoved out of the opening 2204 and onto the conveyor 520. The escapementrod 2302 may be actuated by a cylinder 2206. In an example embodiment,the cylinder 2206 is a pneumatic cylinder. In a particular embodiment,the cylinder is a Bimba Original Line, pneumatic, single rod cylinder.Other embodiments of cylinders may be used as the cylinder 2206.

FIG. 24 illustrates an example control subsystem 402 that may bedeployed in the order processing device 102, the accumulation device224, or otherwise deployed in the system 100. One or more modules arecommunicatively coupled and included in the control subsystem 402 toenable control of the accumulation and/or temporary storage operationsof the accumulation device 224. The modules of the control subsystem 402that may be included are an accumulation module 2402 and a releasemodule 2404. Other modules may also be included.

In some embodiments, the modules of the control subsystem 402 may bedistributed so that some of the modules are deployed in the orderprocessing device 102 and some modules are deployed in the accumulationdevice 224. In one embodiment, the modules are deployed in memory andexecuted by a processor coupled to the memory. The functionalitycontained within the modules 2402 and 2404 may be combined into a lessernumber of modules, further divided among a greater number of modules, orredistributed among existing modules. Other configurations including thefunctionality of the modules 2402, 2404 may be used.

The accumulation module 2402 may control the operations of the scanner1004 and, based on the data read from the label 304 of the bottle 302,may determine the holding tube 518 into which the bottle 302 will beplaced. The accumulation module 2402, in some embodiments, controls theoperations of the upper gantry 504 and gripper assembly 516 to performthe operations of gripping and removing the bottle 302 from the pickposition of the rotary wheel 902, moving the bottle 302 to the holdingtube 518 into which the particular bottle 302 is to be placed, andreleasing the bottle 302 into the holding tube 518. The accumulationmodule 2402 may track each bottle 302 for each prescription order ateach location of the bottle 302 as it travels through the system.

The accumulation module 2402 may access data, such as the order data110, the member data 112, the claims data 114, the drug data 116, theprescription data 118, and/or the plan sponsor data 120, associated witha label 304 of a particular bottle 302. Based on such data, theaccumulation module 2404 may identify the particular holding tube 518into which the particular bottle 302 will be placed.

The release module 2404 may control the operations of the lower gantry506 and the unload assembly 702 to perform the steps of moving theunload assembly 702 under a holding tube 518, raising the unloadassembly 702 to insert the cup 2002 of the unload assembly 702 into thebottom of the holding tube 518, thereby engaging the catch assemblyfinger 1504 a, 1504 b, 1504 c, causing the bottle(s) 402 to be releasedfrom the holding tube 518 into the unload assembly tube 704. The releasemodule 2404 may control the operations of the lower gantry 506 and theunload assembly 702 to perform the steps of moving the unload assembly702 to one of the bottle escapements 510, 512, retracting the unload rod2102 to empty the bottle(s) from the unload assembly tube 704 into theescapement tube 2202, and extending the escapement rod 2302 to push thebottle(s) 302 through the opening 2204 and onto the conveyor 520.

The release module 2404 may access data, such as the order data 110, themember data 112, the claims data 114, the drug data 116, theprescription data 118, and/or the plan sponsor data 120, associated witha particular prescription order associated with bottle(s) 302 held inone or more holding tube 518 of the accumulation subsystem 404. Based onsuch data, the release module 2404 may identify a particular holdingtube 518 as a holding tube from which bottle(s) should be emptied andreleased from the accumulation subsystem 404. Such identification may bebased, for example, on a determination that all of the bottles of theparticular prescription order to be accumulated at the accumulationsubsystem 404 of the accumulation device 224 have been placed into oneor more holding tubes 518 of the table assembly 508. In another example,such identification may be based on a determination that all of theother components of the particular prescription order that includes oneor more bottles temporarily stored at the accumulation subsystem 404have been fulfilled or are being fulfilled by another device within thesystem 100.

FIG. 25 illustrates a method 2500 for accumulating pharmaceuticalbottles of a prescription order, according to an example embodiment. Themethod 2500 may be performed by the accumulation device 224, partiallyby the order processing device 114 and partially by the accumulationdevice 224, or may be otherwise performed.

At block 2502, the bottle 302 is received at the accumulation device224. The bottle label 304 is read and the bottle 302 is associated witha prescription order and a holding tube 518 at block 2504. At block2506, the bottle 302 is deposited into the holding tube 518. If, atblock 2508, another bottle 302 associated with the prescription orderwill be received by the accumulation device 224 then, at block 2510, thebottle will be retained in the holding tube 518. This process willcontinue, with additional bottles 302 of the prescription order beingadded to the holding tube 518, until there are no additional bottles 302of the prescription order to be received at the accumulation device 224.

If no additional bottles 302 will be received, but, at block 2512, otherportions of the prescription order are awaiting fulfilment at otherdevices within the system, then, at block 2514, the bottle(s) 302 willbe retained in the holding tube 518 at block 2516 until, at block 2518,input corresponding to completion of fulfilment of the remaining portionof the prescription order is received by the accumulation device 224, atwhich point, at block 2520, the bottle(s) in the holding tube 518 willbe released into the unload assembly tube 704.

If no additional bottles 302 will be received, and, at block 2512, noother portion of the prescription order is awaiting fulfillment atanother device within the system 100, then, at block 2514, the bottle(s)302 in the holding tube 518 are released into the unload assembly tube704. Then at block 2516, the bottle(s) are emptied from the unloadassembly tube 704 into the bottle escapement 510, 512.

If, at block 2512, other portions of the prescription order are awaitingfulfilment at other devices within the system, then at block 2518, thebottle(s) 302 will be retained in the holding tube 518. At block 2520,input is received corresponding to completion of fulfillment of theremaining portion of the prescription order. Then, at blocks 2514 and2516, respectively, the bottle(s) 302 are released from the holding tube518, into the unload assembly tube 704 and then into the bottleescapement 510, 512.

FIG. 26 shows a block diagram of a machine in the example form of acomputer system 900 within which a set of instructions may be executedcausing the machine to perform any one or more of the methods,processes, operations, or methodologies discussed herein. The devices102, 106-116 may include the functionality of the one or more computersystems 900. With the functionality loaded into the computer system 900for any of the devices 102, 106-116, then the computer system 900 is adedicated, non-general purpose machine.

In an example embodiment, the machine operates as a standalone device ormay be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a server computer, a client computer, a personal computer(PC), a tablet PC, a gaming device, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, anetwork router, switch or bridge, or any machine capable of executing aset of instructions sequential or otherwise) that specifies actions tobe taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The example computer system 2600 includes a processor 2602 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) or both),a main memory 2604 and a static memory 2606, which communicate with eachother via a bus 2608. The computer system 2600 further includes a videodisplay unit 2610 (e.g., a liquid crystal display (LCD) or a cathode rayholding tube (CRT)). The computer system 2600 also includes analphanumeric input device 2612 (e.g., a keyboard), a cursor controldevice 2614 (e.g., a mouse), a drive unit 2616, a signal generationdevice 2618 (e.g., a speaker) and a network interface device 2620.

The drive unit 2616 includes a computer-readable medium 2622 on which isstored one or more sets of instructions (e.g., software 2624) embodyingany one or more of the methodologies or functions described herein. Thesoftware 2624 may also reside, completely or at least partially, withinthe main memory 2604 and/or within the processor 2602 during executionthereof by the computer system 2600, the main memory 2604 and theprocessor 2602 also constituting computer-readable media.

The software 2624 may further be transmitted or received over a network2626 via the network interface device 2620.

While the computer-readable medium 2622 is shown in an exampleembodiment to be a single medium, the term “computer-readable medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“computer-readable medium” shall also be taken to include any mediumthat is capable of storing or encoding a set of instructions forexecution by the machine and that cause the machine to perform any oneor more of the methodologies of the present disclosure. The term“computer-readable medium” shall accordingly be taken to include, butnot be limited to, solid-state memories, and optical media, and magneticmedia. In some embodiments, the computer-readable medium is anon-transitory computer-readable medium.

The term “based on” or using, as used herein, reflects an open-endedterm that can reflect other elements beyond those explicitly recited.

Certain systems, apparatus, applications or processes are describedherein as including a number of modules. A module may be a unit ofdistinct functionality that may be presented in software, hardware, orcombinations thereof. When the functionality of a module is performed inany part through software, the module includes a computer-readablemedium. The modules may be regarded as being communicatively coupled.

In an example embodiment, a pharmaceutical order filling system includesan order processing device to receive a pharmaceutical order and anaccumulation device communicatively coupled to the order processingdevice. The accumulation device includes a bottle scan and pick assemblyand a table assembly, and the bottle scan and pick assembly isconfigured to receive a first container of the prescription order, placethe first container at a pick position, remove the first container fromthe pick position, and place the first container into a holding tube ofthe table assembly. The bottle scan and pick assembly is furtherconfigured to receive a second container of the prescription order,place the second container at a pick position, remove the secondcontainer from the pick position, and place the second container intothe holding tube of the table assembly. In addition, the accumulationdevice includes an unload assembly with a holding tube and a bottleescapement assembly.

In another example embodiment, a pharmaceutical order filling systemincludes an order processing device to receive a first pharmaceuticalorder and a second pharmaceutical order and an accumulation devicecommunicatively coupled to the order processing device. The accumulationdevice includes a bottle scan and pick assembly and a table assembly,and the table assembly includes a plurality of holding tubes arranged ina plurality of tube clusters. Each tube cluster comprises a catchassembly configured to obstruct each of the plurality of holding tubesof the tube cluster. The bottle scan and pick assembly is configured toreceive a first container of the first prescription order and place thefirst container of the first prescription order into a first one of theplurality of holding tubes of the table assembly, and the bottle scanand pick assembly is further configured to receive a first container ofthe second prescription order and place the first container of thesecond prescription into a second one of the plurality of the holdingtubes of the table assembly. The accumulation device also includes anunload assembly and a bottle escapement assembly, wherein the unloadassembly is configured to empty the first container of the firstprescription order from the first one of the plurality of holding tubesinto an unload assembly tube and to release the first container of thefirst prescription order from the unload assembly tube into the bottleescapement assembly, and the unload assembly is further configured toempty the first container of the second prescription order from thesecond one of the plurality of holding tubes into the unload assemblytube and to release the first container of the second prescription orderfrom the unload assembly tube into the bottle escapement assembly.

In yet another example embodiment, a method of filling a pharmaceuticalorder includes receiving at an order processing device a pharmaceuticalorders prescribing a plurality of pharmaceuticals, filling at anautomated dispensing device a first container with a quantity of a firstpharmaceutical selected from the plurality of pharmaceuticals, routingthe first container to an accumulation device, the accumulation devicecomprising a holding tube, placing the first container in the holdingtube, filling at the automated dispensing device a second container witha quantity of a second pharmaceutical selected from the plurality ofpharmaceuticals, routing the second container to the accumulationdevice, placing the second container in the holding tube to accumulatethe first and second containers, releasing the accumulated first andsecond containers from the holding tube, and routing the first andsecond containers to a packing device.

The inventive subject matter may be represented in a variety ofdifferent embodiments of which there are many possible permutations.

Thus, methods and systems for accumulating prescription bottles for aprescription order are described. Although embodiments of the presentinvention have been described with reference to specific exampleembodiments, it will be evident that various modifications and changesmay be made to these embodiments without departing from the broaderspirit and scope of the embodiments of the invention. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

The methods described herein do not have to be executed in the orderdescribed, or in any particular order. Moreover, various activitiesdescribed with respect to the methods identified herein can be executedin serial or parallel fashion.

In the foregoing Detailed Description, it can be seen that variousfeatures are grouped together in a single embodiment for the purpose ofstreamlining the disclosure. This method of disclosure is not to beinterpreted as reflecting an intention that the claimed embodimentsrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter may lie inless than all features of a single disclosed embodiment. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separate embodiment.

The foregoing description is merely illustrative in nature and is in noway intended to limit the disclosure, its application, or uses. Thebroad teachings of the disclosure can be implemented in a variety offorms. Therefore, while this disclosure includes particular examples,the true scope of the disclosure should not be so limited since othermodifications will become apparent upon a study of the drawings, thespecification, and the following claims. It should be understood thatone or more than one steps within a method may be executed in differentorder (or concurrently) without altering the principles of the presentdisclosure. Further, although each of the embodiments is described aboveas having certain features, any one or more than one of those featuresdescribed with respect to any embodiment of the disclosure can beimplemented in and/or combined with features of any of the otherembodiments, even if that combination is not explicitly described. Inother words, the described embodiments are not mutually exclusive, andpermutations of one or more than one embodiments with one another remainwithin the scope of this disclosure.

Spatial and functional relationships between elements (for example,between modules, circuit elements, semiconductor layers, etc.) aredescribed using various terms, including “connected,” “engaged,”“coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and“disposed.” Unless explicitly described as being “direct,” when arelationship between first and second elements is described in the abovedisclosure, that relationship can be a direct relationship where noother intervening elements are present between the first and secondelements, but can also be an indirect relationship where one or morethan one intervening elements are present (either spatially orfunctionally) between the first and second elements. As used herein, thephrase at least one of A, B, and C should be construed to mean a logical(A OR B OR C), using a non-exclusive logical OR, and should not beconstrued to mean “at least one of A, at least one of B, and at leastone of C.”

In this application, including the definitions below, the term ‘module’or the term ‘controller’ may be replaced with the term ‘circuit.’ Theterm ‘module’ may refer to, be part of, or include: an ApplicationSpecific Integrated Circuit (ASIC); a digital, analog, or mixedanalog/digital discrete circuit; a digital, analog, or mixedanalog/digital integrated circuit; a combinational logic circuit; afield programmable gate array (FPGA); a processor circuit (shared,dedicated, or group) that executes code; a memory circuit (shared,dedicated, or group) that stores code executed by the processor circuit;other suitable hardware components that provide the describedfunctionality; or a combination of some or all of the above, such as ina system-on-chip.

The module may include one or more than one interface circuits. In someexamples, the interface circuits may include wired or wirelessinterfaces that are connected to a local area network (LAN), theInternet, a wide area network (WAN), or combinations thereof. Thefunctionality of any given module of the present disclosure may bedistributed among multiple modules that are connected via interfacecircuits. For example, multiple modules may allow load balancing. In afurther example, a server (also known as remote, or cloud) module mayaccomplish some functionality on behalf of a client module.

The term code, as used above, may include software, firmware, and/ormicrocode, and may refer to programs, routines, functions, classes, datastructures, and/or objects. The term shared processor circuitencompasses a single processor circuit that executes some or all codefrom multiple modules. The term group processor circuit encompasses aprocessor circuitry that, in combination with additional processorcircuits, executes some or all code from one or more than one modules.References to multiple processor circuits encompass multiple processorcircuits on discrete dies, multiple processor circuits on a single die,multiple cores of a single processor circuit, multiple threads of asingle processor circuit, or a combination of the above. The term sharedmemory circuit encompasses a single memory circuit that stores some orall code from multiple modules. The term group memory circuitencompasses a memory circuit that, in combination with additionalmemories, stores some or all code from one or more than one modules.

The term memory circuit is a subset of the term computer-readablemedium. The term computer-readable medium, as used herein, does notencompass transitory electrical or electromagnetic signals propagatingthrough a medium (such as on a carrier wave); the term computer-readablemedium may therefore be considered tangible and non-transitory.Non-limiting examples of a non-transitory, tangible computer-readablemedium are nonvolatile memory circuits (such as a flash memory circuit,an erasable programmable read-only memory circuit, or a mask read-onlymemory circuit), volatile memory circuits (such as a static randomaccess memory circuit or a dynamic random access memory circuit),magnetic storage media (such as an analog or digital magnetic tape or ahard disk drive), and optical storage media (such as a CD, a DVD, or aBlu-ray Disc).

The apparatuses and methods described in this application may bepartially or fully implemented by a special purpose computer created byconfiguring a general purpose computer to execute one or more than oneparticular functions embodied in computer programs. The functionalblocks and flowchart elements described above serve as softwarespecifications, which can be translated into the computer programs bythe routine work of a skilled technician or programmer.

The computer programs include processor-executable instructions that arestored on at least one non-transitory, tangible computer-readablemedium.

The invention claimed is:
 1. A pharmaceutical order filling systemcomprising: an order processing device to receive a prescription order;and an accumulation device communicatively coupled to the orderprocessing device, the accumulation device comprising a bottle scan andpick assembly and a table assembly, wherein the bottle scan and pickassembly is configured to receive a first bottle of the prescriptionorder, place the first bottle at a pick position, remove the firstbottle from the pick position, and place the first bottle into a holdingtube of the table assembly; wherein the bottle scan and pick assembly isfurther configured to receive a second bottle of the prescription order,place the second bottle at a pick position, remove the second bottlefrom the pick position, and place the second bottle into the holdingtube of the table assembly; and the accumulation device furthercomprising an unload assembly and a bottle escapement assembly, whereinthe unload assembly includes an unload assembly tube.
 2. Thepharmaceutical order filling system of claim 1, wherein the holding tubeis configured to receive the first bottle and the second bottle when thediameter of the first bottle is different than the diameter of thesecond bottle, and wherein the bottle escapement assembly is configuredto push the first and second bottles out of the bottle escapementassembly and onto a conveyor in an upright position.
 3. Thepharmaceutical order filling system of claim 1, wherein the bottleescapement assembly includes an escapement tube and an escapement rod,wherein the escapement tube receives the first bottle from the unloadassembly tube and the escapement rod forces the first bottle out of anopening in the escapement tube onto a conveyor.
 4. The pharmaceuticalorder filling system of claim 1, wherein the first bottle is filled at afirst device of the pharmaceutical order filling system and the secondbottle is filled at a second device of the pharmaceutical order fillingsystem.
 5. The pharmaceutical order filling system of claim 4, whereinthe first device is an automated dispensing device and the second deviceis a manual fulfillment device.
 6. The pharmaceutical order fillingsystem of claim 4, wherein the first device is a first automateddispensing device and the second device is a second automated dispensingdevice.
 7. The order processing device of claim 1, wherein the orderprocessing device is further configured to receive a second prescriptionorder; wherein the bottle scan and pick assembly is configured toreceive a first bottle of the second prescription order, place the firstbottle of the second prescription order at a pick position, remove thefirst bottle of the second prescription order from the pick position,and place the first bottle of the second prescription order into asecond holding tube of the table assembly; and wherein the bottle scanand pick assembly is further configured to receive a second bottle ofthe second prescription order, place the second bottle of the secondprescription order at a pick position, remove the second bottle of thesecond prescription order from the pick position, and place the secondbottle of the second prescription order into the second holding tube ofthe table assembly.
 8. The order processing system of claim 1, whereinthe accumulation device further comprises an upper gantry and the bottlescan and pick assembly comprises a gripper assembly, and wherein thegripper assembly is mounted to a z-axis belt rail of a z-axis assemblyof the upper gantry.
 9. The order processing system of claim 8 whereinthe z-axis assembly of the upper gantry includes a z-axis motorconfigured to power the z-axis belted rail and actuate z-axis movementof the gripper assembly.
 10. The order processing system of claim 1,wherein the accumulation device further comprises a lower gantry,wherein the unload assembly is mounted to a z-axis assembly of the lowergantry, and wherein the z-axis assembly is configured to actuate z-axismovement of the unload assembly.
 11. The order processing system ofclaim 10, wherein the unload assembly comprises a cup disposed at thetop of the unload assembly tube and wherein the cup is configured toenter an open end of the holding tube and to engage a catch assemblyfinger and move the catch assembly finger from a position obstructingthe open end of the holding tube into an unobstructing position whenz-axis movement of the unload assembly is actuated.
 12. The orderprocessing system of claim 1, wherein the bottle scan and pick assemblyfurther comprises a wheel assembly, wherein the wheel assembly isconfigured to singulate a plurality of bottles entering the accumulationdevice.
 13. The order processing system of claim 12, wherein the wheelassembly comprises a rotary wheel and a wrap wheel, wherein a wrap wheelmotor connected to a belt and a spring loaded belt shaft actuates thewrap wheel and rotates one of the bottles within a pocket of the wrapwheel.
 14. The order processing system of claim 1, wherein the tableassembly comprises a tube cluster and wherein the tube cluster comprisesa plurality of holding tubes and a catch assembly.
 15. The orderprocessing system of claim 14, wherein the catch assembly comprises acatch assembly finger that is configured to open to a positionobstructing one of the holding tubes of the tube cluster.
 16. The orderprocessing system of claim 1, wherein the table assembly furthercomprises a plurality of at least approximately 400 holding tubes.
 17. Apharmaceutical order filling system comprising: an order processingdevice to receive a first prescription order and a second prescriptionorder; and an accumulation device communicatively coupled to the orderprocessing device, the accumulation device comprising a bottle scan andpick assembly and a table assembly, the table assembly comprising aplurality of holding tubes arranged in a plurality of tube clusters,each tube cluster of the plurality of clusters including a catchassembly configured to obstruct each of the plurality of holding tubesof the tube cluster; wherein the bottle scan and pick assembly isconfigured to receive a first bottle of the first prescription order andplace the first bottle of the first prescription order into a first oneof the plurality of holding tubes of the table assembly; wherein thebottle scan and pick assembly is further configured to receive a firstbottle of the second prescription order and place the first bottle ofthe second prescription order into a second one of the plurality of theholding tubes of the table assembly; the accumulation device furthercomprising an unload assembly and a bottle escapement assembly, whereinthe unload assembly is configured to empty the first bottle of the firstprescription order from the first one of the plurality of holding tubesinto an unload assembly tube and to release the first bottle of thefirst prescription order from the unload assembly tube into the bottleescapement assembly; and wherein the unload assembly is furtherconfigured to empty the first bottle of the second prescription orderfrom the second one of the plurality of holding tubes into the unloadassembly tube and to release the first bottle of the second prescriptionorder from the unload assembly tube into the bottle escapement assembly.18. The pharmaceutical order filling system of claim 17, wherein thecatch assembly comprises a plurality of catch assembly fingers, whereina respective one of the catch assembly fingers is adapted to open toobstruct a respective one of the holding tubes of the tube cluster. 19.The pharmaceutical order filling system of claim 18, wherein therespective one of the catch assembly fingers is adapted to close into afinger slot to unobstruct the respective one of the holding tubes of thetube cluster.
 20. The pharmaceutical order filling system of claim 19,wherein the unload assembly further comprises a cap removably attachedto the top of the unload assembly tube and wherein the cap is configuredto engage the respective one of the catch assembly fingers and push therespective one of the catch assembly fingers into a position that doesnot obstruct the respective one holding tube.
 21. The pharmaceuticalorder filing system of claim 17 wherein the plurality of holding tubesis supported by a support structure, and wherein the support structurecomprises a base plate and an upper plate.
 22. The pharmaceutical orderfilling system of claim 17, wherein the bottle pick and scan assemblycomprises a rotary assembly, wherein the rotary assembly comprises arotary wheel, wherein the rotary wheel comprises a pocket to receive thefirst bottle, and wherein a rotary assembly motor actuates the rotarywheel.
 23. A method of filling a pharmaceutical order comprising:receiving at an order processing device a pharmaceutical orderprescribing a plurality of pharmaceuticals; filling at an automateddispensing device a first bottle with a quantity of a firstpharmaceutical selected from the plurality of pharmaceuticals; routingthe first bottle to an accumulation device, the accumulation devicecomprising a holding tube; placing the first bottle in the holding tube;filling at the automated dispensing device a second bottle with aquantity of a second pharmaceutical selected from the plurality ofpharmaceuticals; routing the second bottle to the accumulation device;placing the second bottle in the holding tube to accumulate the firstand second bottles; releasing the accumulated first and second bottlesfrom the holding tube; and routing the first and second bottles to apacking device.
 24. The method of claim 23 further comprising cappingeach the first bottle and the second bottles at a capping device beforeit is routed to the accumulation device.
 25. The method of claim 23further comprising selecting a prepackaged quantity of a thirdpharmaceutical selected from the plurality of pharmaceuticals from aunit of use device; wherein the step of releasing the accumulated firstand second bottles from the holding tube is associated with the step ofselecting the prepackaged quantity of the third pharmaceutical selectedfrom the plurality of pharmaceuticals from the unit of use device, androuting the selected prepackaged quantity of the third pharmaceutical tothe packing device.
 26. The method of claim 25, wherein the step ofreleasing the accumulated first and second bottles from the holding tubecomprises engaging a catch assembly finger that is obstructing theholding tube with an unload assembly tube.
 27. The method of claim 23,the second container having a diameter different than the firstcontainer.